home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000408_news@columbia.edu_Thu Dec 8 01:00:18 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA19704
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Tue, 13 Dec 1994 02:24:43 -0500
Received: by apakabar.cc.columbia.edu id AA22876
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Tue, 13 Dec 1994 02:24:35 -0500
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.mathworks.com!news.duke.edu!godot.cc.duq.edu!newsfeed.pitt.edu!gatech!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!csnnews!gfritz
From: gfritz@csn.net (Gary Fritz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Lockup problem
Date: 8 Dec 1994 01:00:18 GMT
Organization: Colorado Supernet
Lines: 29
Message-Id: <3c5lr2$1e7@news-2.csn.net>
References: <3bsjb2$1e1@news-2.csn.net> <3bvci1$lu8@apakabar.cc.columbia.edu>
Nntp-Posting-Host: 199.117.27.22
X-Newsreader: TIN [version 1.2 PL2]
Apparently-To: kermit.misc@watsun.cc.columbia.edu
Frank da Cruz (fdc@watsun.cc.columbia.edu) wrote:
: Did you read the HP-UX section of ckuker.bwr? Quoting:
No, I didn't (blush) but:
: Before you can use serial ports on the HP-9000, you must configure them as
: either "terminals" or "modems" with SAM ("peripheral devices"..."terminals and
: modems"),
The line is configured as such, and works for cu and for dialin.
: Other things to watch out for: bidirectional ttys (see earlier posting about
: this), improperly configured modem (DSR or CTS signals missing, for example),
: or perhaps commands in your .kermrc that might cause the open() to hang:
: "set carrier on nnn", "set flow rts/cts" (when CTS is not being asserted),
: etc.
I don't have a .kermrc. Can you give me a hint what would cause DSR and
CTS signals to be missing?
I'll look for the bidirectional discussion. I have used this line
bidirectionally, so that may be a good lead.
What confuses me is that it *was* working (although VERY slowly) at one time,
and then *something* changed and now it doesn't. I don't know what the
*something* is, but the fact that it used to work would seem to indicate
that it's not a version problem, or anything that hasn't changed in the
meantime. I don't *think* it's the modem, because I've switched modems
since then and it didn't change anything.